Skip to content

fix: changing breakpoint condition has no immediate effect#1407

Merged
sebthom merged 5 commits intoeclipse-lsp4e:mainfrom
sebthom:issue-1406
Nov 18, 2025
Merged

fix: changing breakpoint condition has no immediate effect#1407
sebthom merged 5 commits intoeclipse-lsp4e:mainfrom
sebthom:issue-1406

Conversation

@sebthom
Copy link
Copy Markdown
Member

@sebthom sebthom commented Nov 18, 2025

Fixes #1406

@sebthom sebthom changed the title fix: mitigate random test failures on Windows because of locked resource fix: changing breakpoint condition has no immediate effect Nov 18, 2025
@sebthom sebthom force-pushed the issue-1406 branch 2 times, most recently from 327bda0 to b66300d Compare November 18, 2025 22:09
@sebthom sebthom force-pushed the issue-1406 branch 2 times, most recently from 1eb2726 to bbae58f Compare November 18, 2025 22:33
which may fail with `VersionBumpRequiredException: Only qualifier
changed for (org.eclipse.lsp4e.<module>). Expected to have bigger x.y.z
than what is available in baseline` despite no actual changes in the
reported module and is actually not required for CodeQL.
Copy link
Copy Markdown
Contributor

@mickaelistria mickaelistria left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Verified, and it works well with Wild Web Developer debuggers.
Thanks!

@sebthom sebthom merged commit 5f622ff into eclipse-lsp4e:main Nov 18, 2025
10 of 11 checks passed
@sebthom sebthom deleted the issue-1406 branch November 25, 2025 15:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Changing breakpoint condition has no immediate effect (with Wild Web Developer)

2 participants